Yes Treasury Withdrawals Committed

Cardano Critical Integrations V2

2026-06-09

Summary

RCADA votes YES on Cardano Critical Integrations V2.

This is a cautious YES.

RCADA supports this proposal because Cardano should not fund major ecosystem integrations once and then allow them to degrade due to a lack of maintenance, renewal funding, or operational support. The original Cardano Critical Integrations V1 program was a large Treasury investment, and this proposal is primarily focused on preserving and extending that investment through continued operation of Circle/USDCx, LayerZero, Pyth, and Dune, while adding Fireblocks native Cardano support.

These integrations are important infrastructure for a mature blockchain ecosystem. Stablecoin access, cross-chain messaging, price oracles, analytics infrastructure, and institutional custody support help make Cardano more usable for builders, institutions, exchanges, liquidity providers, dApps, analysts, and end users.

RCADA recognises that the ₳23,000,000 ask is substantial, especially following the prior ₳70,000,000 CCI V1 Treasury allocation. RCADA also recognises that vendor-level costs cannot be fully disclosed due to confidentiality obligations. This creates an accountability challenge, but the proposal includes Intersect administration, the Treasury Reserve Smart Contract Framework, Steering Committee oversight, independent audits, refund circumstances, unused-fund return, and bi-annual reporting.

RCADA supports this proposal as continuity funding for critical integrations, not as unconditional approval of large recurring Treasury renewals.

Key Considerations

  • CCI V2 is primarily a Year 2 maintenance and operations proposal for integrations funded under CCI V1.
  • The proposal covers Circle/USDCx, LayerZero, Pyth Price Feeds, and Dune Analytics.
  • The proposal also includes full native Fireblocks integration for institutional custody and digital asset operations.
  • The total Treasury ask is ₳23,000,000, equal to approximately $5,750,000 at $0.25 per ADA.
  • The proposal follows the prior ₳70,000,000 CCI V1 allocation.
  • The majority of the budget is allocated to integration and maintenance costs.
  • Vendor-level costs are not publicly disclosed due to confidentiality obligations.
  • Intersect administers the funds through the Treasury Reserve Smart Contract Framework.
  • The Pentad Steering Committee provides business direction, prioritisation, and approval of drawdowns.
  • The governance structure is not perfect, but it appears to be the practical mechanism currently available for complex commercial integrations.
  • RCADA believes major ecosystem entities should remain engaged in Cardano governance while the broader community continues growing execution capacity.
  • Future renewal requests should provide clear evidence of usage, uptime, adoption, institutional onboarding, developer impact, and ecosystem value.

What this action does

This Treasury Withdrawal proposal requests ₳23,000,000 for a 12-month Cardano Critical Integrations V2 program.

The proposal funds:

  1. Operations and maintenance for CCI V1 integrations
    • Circle / USDCx
    • LayerZero
    • Pyth Price Feeds
    • Dune Analytics
  2. Fireblocks native Cardano integration
    • Native support for ADA
    • Cardano Native Token support
    • Technical foundations for Cardano-specific workflows such as staking and governance delegation
  3. Enhancement and tooling reserve
    • SDKs
    • Reference implementations
    • Monitoring and alerting
    • Reconciliation tooling
    • Observability tooling
    • Operational automation
    • Builder-facing support around the integrations
  4. Legal, audit, administration, and contingency
    • Due diligence
    • Independent audits
    • Legal and compliance work
    • Contract administration
    • Constitutional oversight

The high-level budget is:

Category Allocation Share
Integration and maintenance costs ₳20,700,000 ~90%
Enhancement and tooling reserve ₳1,150,000 ~5%
Legal, audit, and contract administration ₳1,150,000 ~5%
Total ₳23,000,000 100%

The proposal explicitly excludes:

  • new Tier-1 integrations such as USDT0;
  • LayerZero OFT expansion;
  • additional DeFi, custodial, analytics, and compliance integrations outside the CCI V1 perimeter;
  • dApp grants;
  • individual project investments;
  • external liquidity attraction;
  • DeFi liquidity deployment;
  • marketing, KOL, and events programs;
  • application-layer funding outside the defined integration scope.

Analysis Findings

Constitutional / Guardrails Assessment

  • ✔ The proposal specifies a clear Treasury ask of ₳23,000,000.
  • ✔ The proposal identifies the purpose of the withdrawal.
  • ✔ The proposal provides a 12-month delivery window.
  • ✔ The proposal discloses prior Treasury receipt of ₳70,000,000 under CCI V1.
  • ✔ The proposal identifies Intersect as Administrator.
  • ✔ Funds are administered through the Treasury Reserve Smart Contract Framework.
  • ✔ The proposal includes a dedicated public address.
  • ✔ The proposal states that funds will not be delegated to an SPO.
  • ✔ The proposal states that funds will be delegated to the predefined auto-abstain voting option.
  • ✔ The proposal includes refund circumstances and unused-fund return.
  • ✔ The proposal includes bi-annual reporting.
  • ✔ The proposal includes audit and compliance commitments.
  • ✔ The proposal requires Statements of Work and defined drawdown conditions.
  • ✔ The proposal identifies explicit exclusions.
  • ⚠ Vendor-level cost disclosure is limited due to confidentiality obligations.
  • ⚠ The proposal relies heavily on Steering Committee judgment and Intersect administration.
  • ⚠ The size of the ask requires strong post-approval reporting and measurable evidence of ecosystem value.

Assessment: Conditional Pass

Process & Governance Quality

  • ✔ The proposal builds on the existing CCI V1 administration structure.
  • ✔ The scope is clearer and narrower than the original CCI V1 package.
  • ✔ The proposal distinguishes maintenance, Fireblocks integration, enhancement reserve, and legal/audit/administration costs.
  • ✔ Explicit exclusions reduce bundling concerns.
  • ✔ Refund circumstances and unused-fund return are positive safeguards.
  • ✔ Bi-annual reporting provides a mechanism for public review.
  • ✔ Steering Committee approval is required for maintenance renewals and enhancement reserve drawdowns.
  • ⚠ The Pentad structure concentrates significant influence among major ecosystem entities.
  • ⚠ The community has limited visibility into vendor-level pricing.
  • ⚠ Future recurring maintenance requests may become difficult to evaluate without clear usage and adoption metrics.
  • ⚠ The community should continue building broader capacity to participate in and eventually share responsibility for major integration programs.

Assessment: Strong structure, with transparency and concentration concerns

Impact & Risk Analysis

  • Infrastructure continuity value: High
  • Strategic integration value: High
  • Institutional readiness value: Medium to High
  • Builder and ecosystem utility: Medium to High
  • Treasury ask size risk: High
  • Vendor-cost opacity risk: Medium to High
  • Recurring dependency risk: Medium to High
  • Governance concentration risk: Medium
  • Administration and safeguard quality: Medium to High

RCADA believes CCI V2 supports important infrastructure continuity. The proposal helps preserve prior Treasury investment and reduce the risk that key integrations degrade after launch. However, the scale of the ask and limited vendor-level disclosure require strong accountability, public reporting, and evidence of ecosystem value.

Assessment: Important infrastructure continuity / cautious support

Ratings (Decision Support Only)

Dimension Score (1–5)
Constitutional clarity 4
Governance quality 4
Execution credibility 4
Ecosystem value 4
Risk balance 3
Overall score 🟡 76% — Cautious YES for continuity of critical integrations

RCADA Rationale

RCADA votes YES on Cardano Critical Integrations V2.

This is a cautious YES.

RCADA supports this proposal because Cardano should not fund major ecosystem integrations once and then allow them to degrade due to a lack of maintenance, renewal funding, or operational support. The original CCI V1 program was a large Treasury investment, and this proposal is primarily focused on preserving and extending that investment through continued operation of Circle/USDCx, LayerZero, Pyth, and Dune, while adding Fireblocks native Cardano support.

These integrations are not abstract. Stablecoin access, cross-chain messaging, oracle feeds, analytics infrastructure, and institutional custody support are important parts of a mature blockchain ecosystem. They help make Cardano more usable for builders, institutions, exchanges, liquidity providers, dApps, analysts, and end users. Cardano cannot reasonably position itself as infrastructure-ready if key integrations are launched but not maintained.

RCADA recognises that the Treasury ask is substantial. At ₳23,000,000, this is a major allocation, especially following the prior ₳70,000,000 CCI V1 budget. We also recognise that most of the budget is allocated to integration and maintenance costs, while specific vendor-level costs cannot be publicly disclosed due to confidentiality obligations. This creates a real accountability challenge for the community.

However, RCADA does not believe the correct response is to abandon or underfund critical infrastructure that the ecosystem has already chosen to pursue. If Cardano funded the first year of these integrations, then the second-year maintenance and renewal question must be handled responsibly. Otherwise, the ecosystem risks wasting prior Treasury investment and weakening the reliability of infrastructure that builders may now depend on.

RCADA also sees the Fireblocks integration as a meaningful addition. Native Cardano support within Fireblocks could reduce friction for exchanges, custodians, fintechs, asset managers, market makers, and other institutional participants that already rely on Fireblocks for digital asset operations. The proposal expects Fireblocks support to include ADA, Cardano Native Tokens, and technical foundations for Cardano-specific workflows such as staking and governance delegation.

RCADA remains cautious about the governance structure. The Pentad Steering Committee concentrates significant influence among major ecosystem entities, including Input Output Global, the Cardano Foundation, EMURGO, Midnight Foundation, and Intersect as non-voting administrator. That concentration should not be ignored, and future governance should continue developing broader community capacity.

At the same time, RCADA believes this concern should be weighed practically. For large commercial integrations involving legal agreements, institutional counterparties, contract renewals, audits, custody, infrastructure maintenance, technical coordination, and partner management, it is not enough to prefer decentralisation in theory. The community also needs entities that are willing, capable, accountable, and legally prepared to execute. At present, the Pentad structure appears to be the practical mechanism available for continuity of CCI V1 and delivery of Fireblocks.

RCADA also believes the major founding and ecosystem entities should not be pushed out or alienated from Cardano governance. They continue to have an important role to play. The healthier path is for the broader community and these institutions to grow together: strengthening transparency, expanding accountability, increasing community participation, and building more distributed execution capacity over time.

The proposal includes several accountability measures that support this cautious YES: Intersect administration, the Treasury Reserve Smart Contract Framework, Steering Committee approval of maintenance and enhancement drawdowns, Statements of Work, dedicated auditable accounts, auto-abstain delegation, no SPO delegation, independent audits, refund circumstances, unused-fund return, and bi-annual reporting on finances, integration status, Fireblocks progress, enhancement reserve activity, audits, and future outlook.

These measures do not remove all concerns. RCADA expects the reports to be specific enough for the community to judge whether CCI V2 is producing real value. Future renewal requests should provide clear evidence of uptime, usage, adoption, developer impact, institutional onboarding, oracle consumption, analytics usage, cross-chain activity, tooling delivery, and any remaining or returned funds.

For these reasons, RCADA votes YES. This vote should be understood as support for continuity of critical integrations and institutional infrastructure, not as unconditional approval of large recurring Treasury renewals. RCADA expects strong reporting, clear evidence of ecosystem value, and continued movement toward broader community capacity in future integration programs.